In-line, in-call AI virtual assistant for teleconferencing

ABSTRACT

Novel tools and techniques for providing an in-line AI virtual assistant are provided. A system includes a session border controller coupled to an end-user device, and a session initiation protocol stack. The session initiation protocol stack includes a processor, and non-transitory computer readable media comprising instructions executable by the processor to: receive, from the session border controller, a call invite request; provision, via the AI virtual assistant service, an AI virtual assistant instance in response to the call invite request; and join the AI virtual assistant instance to a call with the end-user device.

COPYRIGHT STATEMENT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD

The present disclosure relates, in general, to systems for providingin-line call functionality, and more specifically to systems forproviding an in-line call AI assistant in a call path.

BACKGROUND

Artificial intelligence (AI) virtual assistants, also referred to asvoice assistants or personal assistants, have become commonly availablein many devices and for many applications. Virtual assistants are usedto perform various tasks and to answer queries from a user of thevirtual assistant. Typically, virtual assistants are invoked by a useron respective end-devices, which may host the virtual assistant locallyor access the virtual assistant via a network server hosting the virtualassistant. Typically, virtual assistants are invoked by a user through avoice command or by speaking specific term for invoking the virtualassistant. Other examples may include invoking the virtual assistantmanually through one or more input commands such as pressing a button,using a dedicated user interface for interacting with the virtualassistant, opening a program, navigating to a website with the desiredvirtual assistant.

Thus, conventionally, users connect to and interact with a virtualassistant in a point-to-point manner. When users call other parties, ortake part in a teleconference with multiple parties, parties to the callaccess respective instances of a virtual assistant on their ownrespective devices to perform functions and/or answer questions.However, interaction is limited to individual parties and theirrespective virtual assistants, and other parties are not typically ableto interact with others' sessions with their respective virtualassistants.

Accordingly, tools and techniques for providing an in-call, in-line AIvirtual assistant are provided.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the embodimentsmay be realized by reference to the remaining portions of thespecification and the drawings, in which like reference numerals areused to refer to similar components. In some instances, a sub-label isassociated with a reference numeral to denote one of multiple similarcomponents. When reference is made to a reference numeral withoutspecification to an existing sub-label, it is intended to refer to allsuch multiple similar components.

FIG. 1 is a schematic block diagram of a system for providing an in-lineAI virtual assistant, in accordance with various embodiments;

FIG. 2A is a sequence diagram of invoking an in-line AI virtualassistant, in accordance with various embodiments;

FIG. 2B is a sequence diagram of invoking an in-line AI virtualassistant, in accordance with various embodiments;

FIG. 3 is a table of SDP parameters for providing an in-line AI virtualassistant, in accordance with various embodiments;

FIG. 4 is a flow diagram of a method for providing an in-line AI virtualassistant, in accordance with various embodiments;

FIG. 5 is a schematic block diagram of a computer system for providingan in-line AI virtual assistant, in accordance with various embodiments;and

FIG. 6 is a schematic block diagram illustrating system of networkedcomputer devices, in accordance with various embodiments.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

The following detailed description illustrates a few exemplaryembodiments in further detail to enable one of skill in the art topractice such embodiments. The described examples are provided forillustrative purposes and are not intended to limit the scope of theinvention.

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the described embodiments. It will be apparent to oneskilled in the art, however, that other embodiments of the present maybe practiced without some of these specific details. In other instances,certain structures and devices are shown in block diagram form. Severalembodiments are described herein, and while various features areascribed to different embodiments, it should be appreciated that thefeatures described with respect to one embodiment may be incorporatedwith other embodiments as well. By the same token, however, no singlefeature or features of any described embodiment should be consideredessential to every embodiment of the invention, as other embodiments ofthe invention may omit such features.

Unless otherwise indicated, all numbers used herein to expressquantities, dimensions, and so forth used should be understood as beingmodified in all instances by the term “about.” In this application, theuse of the singular includes the plural unless specifically statedotherwise, and use of the terms “and” and “or” means “and/or” unlessotherwise indicated. Moreover, the use of the term “including,” as wellas other forms, such as “includes” and “included,” should be considerednon-exclusive. Also, terms such as “element” or “component” encompassboth elements and components comprising one unit and elements andcomponents that comprise more than one unit, unless specifically statedotherwise.

The various embodiments include, without limitation, methods, systems,and/or software products. Merely by way of example, a method maycomprise one or more procedures, any or all of which are executed by acomputer system. Correspondingly, an embodiment may provide a computersystem configured with instructions to perform one or more procedures inaccordance with methods provided by various other embodiments.Similarly, a computer program may comprise a set of instructions thatare executable by a computer system (and/or a processor therein) toperform such operations. In many cases, such software programs areencoded on physical, tangible, and/or non-transitory computer readablemedia (such as, to name but a few examples, optical media, magneticmedia, and/or the like).

In an aspect, a system for providing an in-line AI virtual assistant.The system includes a session border controller, and a sessioninitiation protocol stack. The session border controller may be coupledto an end-user device, wherein the end-user device is configured toplace a session initiation protocol call to a recipient device. Thesession initiation protocol stack may be in communication with anin-line artificial intelligence (AI) virtual assistant service. Thesession initiation protocol stack further includes a processor, andnon-transitory computer readable media comprising instructionsexecutable by the processor to receive, from the session bordercontroller, a call invite request, provision, via the AI virtualassistant service, an AI virtual assistant instance in response to thecall invite request, and join the AI virtual assistant instance to thesession initiation protocol call with the end-user device.

In another aspect, an apparatus for providing an in-line AI virtualassistant is provided. The apparatus includes a processor, andnon-transitory computer readable media comprising instructionsexecutable by the processor to receive, from a session bordercontroller, a session initiation protocol call invite request,provision, via an artificial intelligence (AI) virtual assistantservice, an AI virtual assistant instance in response to the sessioninitiation protocol call invite request, wherein the AI virtualassistant is provisioned with a respective uniform resource identifier,and join the AI virtual assistant instance to a session initiationprotocol call with an end-user device.

In a further aspect, a method for providing an in-line AI virtualassistant is provided. The method includes receiving, from a sessionborder controller, a call invite request, provisioning, via an AIvirtual assistant service, an artificial intelligence (AI) virtualassistant instance in response to the call invite request, wherein theAI virtual assistant is provisioned with a respective uniform resourceidentifier, and joining, via a session initiation protocol stack, the AIvirtual assistant instance to a session initiation protocol call with anend-user device.

Various modifications and additions can be made to the embodimentsdiscussed without departing from the scope of the invention. Forexample, while the embodiments described above refer to specificfeatures, the scope of this invention also includes embodiments havingdifferent combination of features and embodiments that do not includeall the above described features.

FIG. 1 is a schematic block diagram of a system 100 for providing anin-line AI virtual assistant. In various embodiments, the system 100includes a session border controller (SBC) (commonly referred to as agateway) 105, end-user device 110, local AI virtual assistant 115,monitoring device 120, AI virtual assistant 125, customer network 130,provider network 135, a recipient SBC 140, recipient device 145,recipient local AI virtual assistant 150, AI virtual assistant device155, a webservice/session initiation protocol (SIP) stack 160,webservice 165, and one or more AI virtual assistant instances 170 a-170n. It should be noted that the various components of the system 100 areschematically illustrated in FIG. 1 , and that modifications to thesystem 100 may be possible in accordance with various embodiments.

In various embodiments, the SBC 105 may be coupled to an end-user device110, which may further include a local AI virtual assistant 115. The SBC105 may further be coupled to a monitoring device 120, which may includea second AI virtual assistant 125. The SBC 105 may be coupled to acustomer network 130, and further the customer network 13 may be coupledto the provider network 135. The provider network 135 may further becoupled to a second SBC 140, which may in turn be coupled to a recipientdevice 145 and AI virtual assistant device 155. The recipient device 145may further include an AI virtual assistant 150. The provider network135 may also be coupled to a webservice/SIP stack 160, which may becoupled to the webservice 165. The webservice 165 may include one ormore AI virtual assistant instances 170 a-170 n. In some embodiments,the webservice/SIP stack 160 may alternatively be coupled to themonitoring device 120, which may be coupled to the webservice 165.

In various embodiments, the SBC 105 may be associated with an end-userdevice 110, and through which a user may place a call to a recipient.Accordingly, the SBC 105 may be coupled to one or more client devices,including the end-user device 110, and be configured to route, receive,and manage calls over the customer network 110. End-user device 105 maytherefore include, without limitation, telephone (e.g., VoIP phones,smartphones), computers, tablets, or any other device capable of runninga calling client (e.g., VoIP client) and/or otherwise make calls (e.g.,voice, video, and/or text). In some embodiments, the SBC 105 may beconfigured to manage call data within an enterprise network environment,managing calls between client devices on the enterprise network, andcalls with external parties. In further embodiments, the SBC 105 may bedeployed by a service provider and configured to service one or moreindividual customers of the service provider.

The SBC 105 may be configured to include a SIP server table includingone or more unique uniform resource identifiers (URIs), respectivelyassigned to each client device managed by the SBC 105, including theend-user device 110. The URI may include, for example, a SIP address forthe end-user device 110, and in some embodiments, the monitoring device120. In some embodiments, the monitoring device 120 may be a devicelocated on the customer network 130, and coupled to the SBC 105. In someexamples, when a call is initiated by the end-user device 110 to arecipient device 145, the end-user device 110 may be configured torequest that the monitoring device 120 join the call, or be added to thecall by the SBC 105. For example, the SBC the end-user device 105 maygenerate a request that the monitoring device 120 join the call, or thatthe monitoring device 120 be added to the call. The SBC 105 may theninvite the monitoring device 120 to join the call, or the monitoringdevice 120 may be added to the call by the SBC 105. Alternatively, insome embodiments, each time a call is initiated by the end-user device110, the SBC 105 may be configured to automatically join the monitoringdevice 120 in the call. Thus, in some embodiments, the SBC 105 may beconfigured to automatically invite and/or join a dedicated monitoringdevice 120. When a call is made by the end-user device 110, a three-waycall, conference, or other multiple-party call may be initiated toinclude the monitoring device 120. Automatically included or invoked.

Alternatively, in some embodiments, the monitoring device 120 may bepart of a webservice/SIP stack 160 for the AI virtual assistant. Thus,each time a call is placed by the end-user device 110, the SBC 105 maysend in invite to the monitoring device 120 via the webservice/SIP stack160. The webservice SIP stack 160 may then invite the monitoring device120 to join the call, or otherwise add the monitoring device 120 to thecall. For example, in some embodiments, the webservice/SIP stack 160 maybe configured to determine whether a user associated with the end-userdevice 110 is authorized to invoke the AI virtual assistant 125, 170a-170 n function of the webservice 165. If it is determined that theuser is authorized to access the webservice 165, the webservice/SIPstack 160 may further be configured to connect the monitoring device 120to the call.

In further embodiments, an AI virtual assistant device 155 may be joinedto the call via a recipient SBC 140. For example, when a call is placedto the recipient device 145, the recipient SBC 140 may automaticallyconnect the AI virtual assistant device 155 to the call. As previouslydescribed, the recipient SBC 140 may be configured to joint he AIvirtual assistant device 155 as a three-way call, conference call, orother multi-party call. Thus, in some examples, the AI virtual assistantdevice 155 may also be a monitoring device, like the monitoring device120.

In various embodiments, the SBC 105 and/or recipient SBC 140, andwebservice/SIP stack 160 may be configured to determine whether acustomer (e.g., the party invoking the AI virtual assistant 115, 125,150, 155, 170 a-170 n) is authorized to receive the service. Forexample, in some embodiments, in various embodiments, a party on thecall may invoke the AI virtual assistant. The party invoking the AIvirtual assistant may, in some examples, be unknown to the SBC 105,recipient SBC 140, and/or webservice/SIP stack 160. Accordingly, the SBC105, recipient SBC 140, and/or the webservice/SIP stack 160 may beconfigured to determine whether any party in the call/session isauthorized to invoke the AI virtual assistant 115, 125, 150, 155, 170a-170 n. In some further embodiments, the monitoring device 120 may beadded to the call in response to a determination that a party in thecall is authorized to invoke the AI virtual assistant 115, 125, 150,155, 170 a-170 n. If it is determined that a party in the call isauthorized to invoke the AI virtual assistant 125, the SBC 105,recipient SBC 140, and/or webservice/SIP stack 160 mayinitialize/provision an AI virtual assistant instance 170 a-170 n, whichmay further be added to the call by the SBC 105, recipient SBC 140,and/or webservice/SIP stack 160 as appropriate. For example, in someembodiments, the AI virtual assistant instance 170 a-170 n may beprovisioned by the webservice 165 as an additional party with arespective URI to be added to the call. Accordingly, in variousembodiments, the webservice/SIP stack 160 may include, withoutlimitation, one or more server computers configured to provide the AIvirtual assistant service and run a SIP stack to manage calls to variousAI virtual assistant instances.

In some further embodiments, the AI virtual assistant 115 may be aninstance of the AI virtual assistant that runs locally on an end-userdevice. Accordingly, the AI virtual assistant 115 may have a URIseparate from the URI of the end-user device 110 via which a caller maycommunicate. For example, in some embodiments, the local AI virtualassistant 115 may include a virtual machine to which a respective URI isassigned, and through which the local AI virtual assistant 115 may joina call. Accordingly, in some embodiments, in response to a determinationthat the user is authorized to invoke the AI virtual assistant 115, 125,150, 155, a respective local instance of an AI virtual assistant 115,125, 150, 155 may be authorized to be added to the call. Similarly, insome embodiments, the recipient device 145 may include a recipient localAI virtual assistant 150, which may have a separate URI from therecipient device 145.

In various embodiments, the monitoring device 120 and/or AI virtualassistant device 155 may be configured to determine whether a party onthe call has invoked the AI virtual assistant 115, 125, 150, 155, 170a-170 n. For example, in some embodiments, the monitoring device may beconfigured to monitor call audio for a wake word to be spoken by aparticipant on the call. A wake word may include a word configured to,when spoken, invoke and/or request an AI virtual assistant 115, 125,150, 155, 170 a-170 n to join the call. Thus, when the monitoring device120 and/or AI virtual assistant device 155 determines that a user hasspoken the wake word, in some embodiments, the monitoring device 120and/or AI virtual assistant device 155 may send a call invite to thewebservice 165 and/or a specific AI virtual assistant instance 170 a-170n, via the webservice/SIP stack 160. In further embodiments, a local AIvirtual assistant 125, 115, 155, 150 may be joined into the call. Insome further embodiments, the monitoring device 120 may additionallyand/or alternatively be configured to determine whether a touch tone(e.g., dual-tone multi-frequency signaling) code configured to invokethe AI virtual assistant 115, 125, 150, 155, 170 a-170 n has beenentered by a participant on the call. If it is determined that the touchtone code has been entered by a participant, the monitoring device 120and/or AI virtual assistant device 155 may similarly send a call inviteto the webservice 165 and/or a specific AI virtual assistant instance170 a-170 n, via the webservice/SIP stack 160.

In some embodiments, the monitoring device 120 may be configured toinvoke an AI virtual assistant instance 115, 125, 150, 155, 170 a-170 n.For example, in some embodiments, the monitoring device 120 may includean AI virtual assistant 125 instance. Alternatively, monitoring device120 may invoke the webservice 165 via the webservice/SIP stack 160. Forexample, the monitoring device 120 may cause the SBC 105 to invite thewebservice 165 to the call. Similarly, in some embodiment, the AIvirtual assistant device 155 may be configured to invoke the webservice165 via the webservice SIP stack 160. Thus, in some examples, the AIvirtual assistant device 155 may generate an INVITE SIP message to besent, via the recipient SBC 140, to the webservice/SIP stack 160, whichmay in turn invoke a respective AI virtual assistant instance 170 a-170n of the webservice 165. Similarly, AI virtual assistant device 155 maybe a combination of a monitoring device and a local AI virtual assistantinstance.

FIGS. 2A & 2B are sequence diagrams 200A, 200B of a process for invokingan in-line AI virtual assistant, in accordance with various embodiments.The sequence diagram 200A includes user A 205, SBC/media gateway 210,user B 215, webservice/SIP stack 220, and AI virtual assistant service225. The AI virtual assistant service 225 may further be coupled to oneor more tools and functionalities. The one or more tools andfunctionalities may include a calendar 230, email 235, teleconferenceschedule 240, a chat bot 245, and other tools 250. It should be notedthat the various components of the sequence diagram 200A and 200B areschematically illustrated in FIGS. 2A & 2B, and that modifications tothe sequence diagram 200A and 200B may be possible in accordance withvarious embodiments.

In various embodiments, the user A 205 may be a URI of an end-userdevice associated with a first user (user A). The SBC/media gateway 210may be an SBC located and/or gateway device located between user A 205and user B 215. For example, the SBC 210 may be an SBC located on alocal network of the user A, or an SBC associated with a serviceprovider providing voice service to one or more of user A 205 or user B215. User B 215, therefore, may be a URI of a recipient deviceassociated with a recipient (user B). The webservice/SIP stack 220 maybe an SIP stack (including, without limitation, one or more of an SIPserver, SBC, or media gateway) associated with a webservice. Thewebservice, in some embodiments, includes the AI virtual assistantservice 225. Accordingly, the AI virtual assistant service 225 mayinclude one or more AI virtual assistant instances that may beprovisioned with a respective URI. Each AI virtual assistant instancemay further be configured to access one or more additional tools, suchas the calendar 230, email 235, teleconference schedule 240, chat bot245, and/or other tools 250.

In various embodiments, the calendar 230 tool may be configured toaccess an electronic calendar associated with one or more participantsof a call, including user A 205 and user B 215. Accordingly, thecalendar tool 230 may be configured to interface with one or moreelectronic calendars associated with one or more of the user A 205 anduser B 215. Furthermore, each of the one or more electronic calendarsmay be associated with respective service providers and/or electronicaccounts. Similarly, email tool 235 may be configured to interface withone or more email accounts of one or more call participants, includinguser A 205 and user B 215. The calendar tool 230 and email tool 235 maybe configured to allow an AI virtual assistant instance to access acalendar and/or email account, and access items within the calendarand/or email accounts, associated with one or more the callparticipants, as described above. The teleconference schedule tool 240may include a schedule for a teleconference line on which the callparticipants may be conducting a call. The chat bot tool 245 may, insome embodiments, include a text-based and/or speech-to-text bot forcommunicating with call participants via text-based messages and/ordata. The chat bot 245 may further include voice communicationfunctionality configured to allow an AI virtual assistant instance tocommunicate using speech/audio data. In some embodiments, other tools250 may include, without limitation, search functionality (e.g., websearch), video and/or image analysis, voice analysis, file transfer,storage device interfaces, weather tools, and/or otherapplication/service specific APIs to interface with various otherapplications and services.

In one set of embodiments, a call may begin with user A 205 placing acall to user B 215. Accordingly, the sequence diagram illustrates anexemplary set of SIP messages that may be passed between the variousdevices/components to place the call. For examples, to initiate a call,an INVITE request, INVITE B, may be sent by user A to the SBC/mediagateway 210. The SBC/media gateway 210 may then route the call (e.g.,the INVITE message) to user B 215. The SBC/media gateway 210 may replyto user A 205 with a response, 100 Trying, to indicate that the requesthas been received by the next-hop server (e.g., a subsequent SBC) and/orthe user B 215. User B may respond to the SBC with a 180 Ringingresponse, indicating that the INVITE request is ringing/alerting user B215. SBC 210 may forward the 180 Ringing response to user A 205. If thecall is successful, user B 215 may submit a 200 OK response to theSBC/media gateway 210, indicating that the INVITE request as succeeded,which is in turn forwarded by the SBC/media gateway 210 to the user A205. An ACK response may then be transmitted by the user A 215 to theuser B 215, in response to the 200OK response. Although subsequentresponses of the sequence diagram 200A, 200B are depicted as beingtransmitted directly to user A 205, user B 215, webservice/SIP stack220, and AI virtual assistant service 225, it should be understood thatmessages may still traverse any intermediate next-hop servers duringtransmission to the intended destination.

Once an ACK response is receive, a 2-way real-time transport protocol(RTP) connection may be established between user A 205, and user B 215.The 2-way RTP connection may be configured to carry RTP media data, suchas voice data between the user A 205 and user B 215. In someembodiments, RTP media data may further include, without limitation,other audio data, video data, and/or text data to be passed betweenconnected parties.

As previously described, in various embodiments, a monitoring device mayfurther be joined to the call. For example, in some embodiments, amonitoring device may be invited, via the webservice/SIP stack 220. Inone example, the user B 215 may send a send-only request (INVITEsendonly) to user A, which causes user A 205 to send RTP media data, butnot receive RTP media data. The user A 205 may send response 200 OK, atwhich point an ACK response may be sent by user B 215 to user A 205.Concurrently, the RTP connection may be put on hold, while user B sendsan INVITE C request to a third party, in this example the webservice/SIPstack 220 of the AI virtual assistant service 225. It is to beunderstood that in other embodiments, the invite request towebservice/SIP stack 220 may originate from user A 205, in which casethe user B 215 may be put in send-only mode. Alternatively, in someembodiments, in the case of a separate monitoring device, the separatemonitoring device may be similarly be invited as a third party to thecall. Once a wake word and/or DTMF code has been entered by a party tothe call, the monitoring device may generate the invite request INVITE Cto the webservice/SIP stack 220.

The webservice/SIP stack 220 may then send an InvokeAIservice request tothe AI virtual assistant service 225, which may request that the AIvirtual assistant service 225 provision an AI virtual assistant instanceto be connected to the call. Thus, after sending the InvokeAIservicerequest, the webservice/SIP stack 220 may respond with a 180 Ringingresponse to user B 215 (or alternatively user A 205). Once the AIvirtual assistant instance has been provisioned and able to be connectedto the call, a Success response may be provided to the webservice/SIPstack 220. The webservice/SIP stack 200 may in turn provide a 200 OKresponse to the user B 215 (or alternatively user A 205, as the case maybe). An ACK response may be sent to the webservice/SIP stack 220 inresponse, and a 2-way RTP connection established between the AI virtualassistant service 225 (e.g., the AI virtual assistant instance) and theuser B 215 (or user A).

Once the RTP channel with the AI virtual assistant instance has beenestablished, the user B 215 may send an INVITE sendrecv request to userA 205 to put the user A 205 back into both send and receive mode. TheRTP connection between user A 205 and user b 215 may further be takenoff-hold, and an RTP conference channel established between user A 205,user B 215, and the AI virtual assistant service 225 (in this case theAI virtual assistant instance provisioned to the call by the AI virtualassistant service 225).

In some embodiments, the AI virtual assistant instance may itselfinclude a monitoring device for determining whether the AI virtualassistant has been invoked by a party on the call (e.g., a wake wordspoken, or DTMF code entered). Once the AI virtual assistant has beeninvoked by a party, the AI virtual assistant may be configured toperform one or more actions in response to a query or command from oneor more participants to the call. For example, the AI virtual assistantmay be configured to utilize the one or more tools, such as calendartool 230, email tool 235, teleconference schedule 240, chat bot 245, orother tools 250 as previously described.

FIG. 3 is a table of session description protocol (SDP) parameters 300for providing an in-line AI virtual assistant, in accordance withvarious embodiments. The SDP parameters 300 may include sessiondescriptions 303, time descriptions 305, and media descriptions 307. Itshould be noted that the various SDP parameters and description fields300 are schematically illustrated in FIG. 3 , and that modifications tothe SDP parameters 300 may be possible in accordance with variousembodiments.

Session description 303 may include one or more session descriptionfields 309. The session description fields 309 may include varioussession description fields as known to those in the art, such as:

-   -   v=(protocol version)    -   o=(owner/creator and session identification)    -   s=(session name)    -   i=* (session information)    -   u=* (URI of description)    -   e=* (email address)    -   p=* (phone number)    -   c=* (connection information)    -   b=* (session bandwidth information)    -   z=* (time zone adjustments)    -   k=* (encryption key)

Similarly, time description 305 may include one or more time descriptionfields 323 as known to those in the art. Time description fields 323 mayinclude, without limitation:

-   -   t=* (time the session is active)    -   r=* (repeat times)

Media description 307 may include one or more media description fields325. The one or more media description fields may include, withoutlimitation:

-   -   m=(media name/transport address)    -   i=* (media title)    -   c=* (connection information)    -   b=* (bandwidth information)    -   k=* (encryption key)

In various embodiments, the one or more session description fields 309may further include the field a=(zero or more session attribute lines)311. Similarly, the one or more media description fields 325 may alsoinclude the field a=(zero or more media attribute lines) 327. In variousembodiments, this session description field a=“session assistant” 313may be configured to invoke the AI virtual assistant. For example, invarious embodiments, the InvokeAIservice request may be a SIP and/or SDPmessage that utilizes the SDP field a=“session assistant” 313 as atrigger to create an INVITE request to a specific AI virtual assistantinstance. Similarly, SIP and/or SDP messages may include mediadescription field a=“session assistant” 329 to further describe mediaThus, the webservice/SIP stack (e.g., webservice/SIP stack 220 of FIG. 2) may accordingly be configured to support the trigger, which mayinclude the specific session description field a=“session assistant” 313to designate/describe RTP media from/to an AI virtual assistantinstance.

FIG. 4 is a flow diagram of a method 400 for providing an in-line AIvirtual assistant. The method 400 begins, at optional block 405, bydetermining whether a user is authorized to invoke an AI virtualassistant. As previously described, in some embodiments, an SBC may beconfigured to determine whether a user is authorized to invoke an AIvirtual assistant. In other embodiments, a monitoring device may beconfigured to be connected to calls made by a user. The monitoringdevice may then be configured to whether the user is authorized toinvoke the AI virtual assistant.

The method 400 continues, at block 410, by determining that a call hasbeen placed by the user. Once it is determined that a call has beenplaced, the method may continue, at optional block 415, by joining amonitoring device to the call. As previously described, in someembodiments, the caller, call recipient, and/or an SBC may be configuredto generate an invite request and/or otherwise cause a monitoring deviceto join the call.

At optional block 420, the monitoring device may determine whether theAI virtual assistant has been invoked. As previously described, themonitoring device may be configured to determine whether a participanton the call has spoken a wake word and/or entered a touch tone code forinvoking the AI virtual assistant.

The method 400 continues, at block 425, by generating a call request tothe AI virtual assistant webservice. As previously described, in someembodiments, a call participant and/or SBC may be configured to generatean INVITE request to be sent to the webservice/SIP stack associated withthe AI virtual assistant. Thus, in effect, the call request istransmitted to a webservice/SIP stack. In some further embodiments, aseparate monitoring device may be configured to generate a call invite(e.g., INVITE request) to the AI virtual assistant webservice. In otherembodiments, the AI virtual assistant may itself act as a monitoringdevice once added to a call.

Accordingly, at block 540, the method continues by provisioning an AIvirtual assistant instance to join the call. As previously described,the webservice may be configured to provision an AI virtual assistantinstance in response to receiving an INVITE request from an authorizeduser and/or SBC associated with an authorized user of the AI virtualassistant webservice.

The method continues, at block 435, by joining the AI virtual assistantinstance to the call. As previously described, the AI virtual assistantinstance may be provisioned with a unique respective URI, and managedvia the webservice/SIP stack. Accordingly, the webservice/SIP stack maybe configured to establish a connection between AI virtual assistantinstance and a caller. In some embodiments, joining the AI virtualassistant instance to the call may include establishing an RTPconference connection between at least 2 existing call parties, and/or a2-way connection to a party invoking the AI virtual assistant.

At optional block 440, as previously described, the method 400 maycontinue by determining that the AI virtual assistant has been invokedvia media data from the call. RTP media data may be analyzed by the AIvirtual assistant, or alternatively a monitoring device. In someembodiments, determining that an AI virtual assistant has been invokedmay include monitoring voice/audio data for wake words and/or aDTMF/touch tone code. In other embodiments, the AI virtual assistant maybe configured to be invoked by text data transmitted over the call.

At optional block 445, in response to determining that the AI virtualassistant has been invoked, the method 400 may continue by performingone or more actions based on a user voice query and/or command asdetermined from the call voice data. In some embodiments, media data mayinclude audio (e.g., voice), video, and/or text data.

FIG. 5 is a schematic block diagram of a computer system 500 forproviding an in-line Ai virtual assistant, in accordance with variousembodiments. The computer system 500 is a schematic illustration of acomputer system (physical and/or virtual), such as an SBC,webservice/SIP stack, monitoring device, end-user device, AI virtualassistant instance, and/or dedicated AI virtual assistant device, whichmay perform the methods provided by various other embodiments, asdescribed herein. It should be noted that FIG. 5 only provides ageneralized illustration of various components, of which one or more ofeach may be utilized as appropriate. FIG. 5 , therefore, broadlyillustrates how individual system elements may be implemented in arelatively separated or relatively more integrated manner.

The computer system 500 includes multiple hardware (or virtualized)elements that may be electrically coupled via a bus 505 (or mayotherwise be in communication, as appropriate). The hardware elementsmay include one or more processors 510, including, without limitation,one or more general-purpose processors and/or one or morespecial-purpose processors (such as microprocessors, digital signalprocessing chips, graphics acceleration processors, andmicrocontrollers); one or more input devices 515, which include, withoutlimitation, a mouse, a keyboard, one or more sensors, and/or the like;and one or more output devices 520, which can include, withoutlimitation, a display device, and/or the like.

The computer system 500 may further include (and/or be in communicationwith) one or more storage devices 525, which can comprise, withoutlimitation, local and/or network accessible storage, and/or can include,without limitation, a disk drive, a drive array, an optical storagedevice, solid-state storage device such as a random-access memory(“RAM”) and/or a read-only memory (“ROM”), which can be programmable,flash-updateable, and/or the like. Such storage devices may beconfigured to implement any appropriate data stores, including, withoutlimitation, various file systems, database structures, and/or the like.

The computer system 500 may also include a communications subsystem 530,which may include, without limitation, a modem, a network card (wirelessor wired), an IR communication device, a wireless communication deviceand/or chip set (such as a Bluetooth™ device, an 802.11 device, a WiFidevice, a WiMax device, a WWAN device, a low-power (LP) wireless device,a Z-Wave device, a ZigBee device, cellular communication facilities,etc.). The communications subsystem 530 may permit data to be exchangedwith a network (such as the network described below, to name oneexample), with other computer or hardware systems, between data centersor different cloud platforms, and/or with any other devices describedherein. In many embodiments, the computer system 500 further comprises aworking memory 535, which can include a RAM or ROM device, as describedabove.

The computer system 500 also may comprise software elements, shown asbeing currently located within the working memory 535, including anoperating system 540, device drivers, executable libraries, and/or othercode, such as one or more application programs 545, which may comprisecomputer programs provided by various embodiments, and/or may bedesigned to implement methods, and/or configure systems, provided byother embodiments, as described herein. Merely by way of example, one ormore procedures described with respect to the method(s) discussed abovemay be implemented as code and/or instructions executable by a computer(and/or a processor within a computer); in an aspect, then, such codeand/or instructions can be used to configure and/or adapt a generalpurpose computer (or other device) to perform one or more operations inaccordance with the described methods.

A set of these instructions and/or code may be encoded and/or stored ona non-transitory computer readable storage medium, such as the storagedevice(s) 525 described above. In some cases, the storage medium may beincorporated within a computer system, such as the system 500. In otherembodiments, the storage medium may be separate from a computer system(i.e., a removable medium, such as a compact disc, etc.), and/orprovided in an installation package, such that the storage medium can beused to program, configure, and/or adapt a general purpose computer withthe instructions/code stored thereon. These instructions may take theform of executable code, which is executable by the computer system 500and/or may take the form of source and/or installable code, which, uponcompilation and/or installation on the computer system 500 (e.g., usingany of a variety of generally available compilers, installationprograms, compression/decompression utilities, etc.) then takes the formof executable code.

It will be apparent to those skilled in the art that substantialvariations may be made in accordance with specific requirements. Forexample, customized hardware (such as programmable logic controllers,single board computers, FPGAs, ASICs, and SoCs) may also be used, and/orparticular elements may be implemented in hardware, software (includingportable software, such as applets, etc.), or both. Further, connectionto other computing devices such as network input/output devices may beemployed.

As mentioned above, in one aspect, some embodiments may employ acomputer or hardware system (such as the computer system 500) to performmethods in accordance with various embodiments of the invention.According to a set of embodiments, some or all of the procedures of suchmethods are performed by the computer system 500 in response toprocessor 510 executing one or more sequences of one or moreinstructions (which may be incorporated into the operating system 540and/or other code, such as an application program 545 or firmware)contained in the working memory 535. Such instructions may be read intothe working memory 535 from another computer readable medium, such asone or more of the storage device(s) 525. Merely by way of example,execution of the sequences of instructions contained in the workingmemory 535 may cause the processor(s) 510 to perform one or moreprocedures of the methods described herein.

The terms “machine readable medium” and “computer readable medium,” asused herein, refer to any medium that participates in providing datathat causes a machine to operate in a specific fashion. In an embodimentimplemented using the computer system 500, various computer readablemedia may be involved in providing instructions/code to processor(s) 510for execution and/or may be used to store and/or carry suchinstructions/code (e.g., as signals). In many implementations, acomputer readable medium is a non-transitory, physical, and/or tangiblestorage medium. In some embodiments, a computer readable medium may takemany forms, including, but not limited to, non-volatile media, volatilemedia, or the like. Non-volatile media includes, for example, opticaland/or magnetic disks, such as the storage device(s) 525. Volatile mediaincludes, without limitation, dynamic memory, such as the working memory535. In some alternative embodiments, a computer readable medium maytake the form of transmission media, which includes, without limitation,coaxial cables, copper wire and fiber optics, including the wires thatcomprise the bus 505, as well as the various components of thecommunication subsystem 530 (and/or the media by which thecommunications subsystem 530 provides communication with other devices).In an alternative set of embodiments, transmission media can also takethe form of waves (including, without limitation, radio, acoustic,and/or light waves, such as those generated during radio-wave andinfra-red data communications).

Common forms of physical and/or tangible computer readable mediainclude, for example, a floppy disk, a flexible disk, a hard disk,magnetic tape, or any other magnetic medium, a CD-ROM, any other opticalmedium, punch cards, paper tape, any other physical medium with patternsof holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chipor cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read instructions and/or code.

Various forms of computer readable media may be involved in carrying oneor more sequences of one or more instructions to the processor(s) 510for execution. Merely by way of example, the instructions may initiallybe carried on a magnetic disk and/or optical disc of a remote computer.A remote computer may load the instructions into its dynamic memory andsend the instructions as signals over a transmission medium to bereceived and/or executed by the computer system 500. These signals,which may be in the form of electromagnetic signals, acoustic signals,optical signals, and/or the like, are all examples of carrier waves onwhich instructions can be encoded, in accordance with variousembodiments of the invention.

The communications subsystem 530 (and/or components thereof) generallyreceives the signals, and the bus 505 then may carry the signals (and/orthe data, instructions, etc. carried by the signals) to the workingmemory 535, from which the processor(s) 510 retrieves and executes theinstructions. The instructions received by the working memory 535 mayoptionally be stored on a storage device 525 either before or afterexecution by the processor(s) 510.

FIG. 6 is a schematic block diagram illustrating system of networkedcomputer devices, in accordance with various embodiments. The system 600may include one or more user devices 605. A user device 605 may include,merely by way of example, desktop computers, single-board computers,tablet computers, laptop computers, handheld computers, edge devices,and the like, running an appropriate operating system. User devices 605may further include external devices, remote devices, servers, and/orworkstation computers running any of a variety of operating systems. Auser device 605 may also have any of a variety of applications,including one or more applications configured to perform methodsprovided by various embodiments, as well as one or more officeapplications, database client and/or server applications, and/or webbrowser applications. Alternatively, a user device 605 may include anyother electronic device, such as a thin-client computer,Internet-enabled mobile telephone, and/or personal digital assistant,capable of communicating via a network (e.g., the network(s) 610described below) and/or of displaying and navigating web pages or othertypes of electronic documents. Although the exemplary system 600 isshown with two user devices 605 a-605 b, any number of user devices 605may be supported.

Certain embodiments operate in a networked environment, which caninclude a network(s) 610. The network(s) 610 can be any type of networkfamiliar to those skilled in the art that can support datacommunications, such as an access network, core network, or cloudnetwork, and use any of a variety of commercially-available (and/or freeor proprietary) protocols, including, without limitation, MQTT, CoAP,AMQP, STOMP, DDS, SCADA, XMPP, custom middleware agents, Modbus, BACnet,NCTIP, Bluetooth, Zigbee/Z-wave, TCP/IP, SNA™, IPX™, and the like.Merely by way of example, the network(s) 610 can each include a localarea network (“LAN”), including, without limitation, a fiber network, anEthernet network, a Token-Ring™ network and/or the like; a wide-areanetwork (“WAN”); a wireless wide area network (“WWAN”); a virtualnetwork, such as a virtual private network (“VPN”); the Internet; anintranet; an extranet; a public switched telephone network (“PSTN”); aninfra-red network; a wireless network, including, without limitation, anetwork operating under any of the IEEE 802.11 suite of protocols, theBluetooth™ protocol known in the art, and/or any other wirelessprotocol; and/or any combination of these and/or other networks. In aparticular embodiment, the network may include an access network of theservice provider (e.g., an Internet service provider (“ISP”)). Inanother embodiment, the network may include a core network of theservice provider, backbone network, cloud network, management network,and/or the Internet.

Embodiments can also include one or more server computers 615. Each ofthe server computers 615 may be configured with an operating system,including, without limitation, any of those discussed above, as well asany commercially (or freely) available server operating systems. Each ofthe servers 615 may also be running one or more applications, which canbe configured to provide services to one or more clients 605 and/orother servers 615.

Merely by way of example, one of the servers 615 may be a data server, aweb server, orchestration server, authentication server (e.g., TACACS,RADIUS, etc.), cloud computing device(s), or the like, as describedabove. The data server may include (or be in communication with) a webserver, which can be used, merely by way of example, to process requestsfor web pages or other electronic documents from user computers 605. Theweb server can also run a variety of server applications, including HTTPservers, FTP servers, CGI servers, database servers, Java servers, andthe like. In some embodiments of the invention, the web server may beconfigured to serve web pages that can be operated within a web browseron one or more of the user computers 605 to perform methods of theinvention.

The server computers 615, in some embodiments, may include one or moreapplication servers, which can be configured with one or moreapplications, programs, web-based services, or other network resourcesaccessible by a client. Merely by way of example, the server(s) 615 canbe one or more general purpose computers capable of executing programsor scripts in response to the user computers 605 and/or other servers615, including, without limitation, web applications (which may, in somecases, be configured to perform methods provided by variousembodiments). Merely by way of example, a web application can beimplemented as one or more scripts or programs written in any suitableprogramming language, such as Java™, C, C#™ or C++, and/or any scriptinglanguage, such as Perl, Python, or TCL, as well as combinations of anyprogramming and/or scripting languages. The application server(s) canalso include database servers, including, without limitation, thosecommercially available from Oracle™, Microsoft™, Sybase™, IBM™, and thelike, which can process requests from clients (including, depending onthe configuration, dedicated database clients, API clients, webbrowsers, etc.) running on a user computer, user device, or customerdevice 605 and/or another server 615.

In accordance with further embodiments, one or more servers 615 canfunction as a file server and/or can include one or more of the files(e.g., application code, data files, etc.) necessary to implementvarious disclosed methods, incorporated by an application running on auser computer 605 and/or another server 615. Alternatively, as thoseskilled in the art will appreciate, a file server can include allnecessary files, allowing such an application to be invoked remotely bya user computer, user device, or customer device 605 and/or server 615.

It should be noted that the functions described with respect to variousservers herein (e.g., application server, database server, web server,file server, etc.) can be performed by a single server and/or aplurality of specialized servers, depending on implementation-specificneeds and parameters.

In certain embodiments, the system can include one or more databases 620a-620 n (collectively, “databases 620”). The location of each of thedatabases 620 is discretionary: merely by way of example, a database 620a may reside on a storage medium local to (and/or resident in) a server615 a (or alternatively, user device 605). Alternatively, a database 620n can be remote so long as it can be in communication (e.g., via thenetwork 610) with one or more of these. In a particular set ofembodiments, a database 620 can reside in a storage-area network (“SAN”)familiar to those skilled in the art. In one set of embodiments, thedatabase 620 may be a relational database configured to host one or moredata lakes collected from various data sources. The databases 620 mayinclude SQL, no-SQL, and/or hybrid databases, as known to those in theart. The database may be controlled and/or maintained by a databaseserver.

The system 600 may further include an end-user device 625, SBC 630,webservice/SIP stack 635, AI virtual assistant service 640, andrecipient device 645. In various embodiments, the end-user device 625may include a device from which a caller may place a call to therecipient device 645, Accordingly, the end-user device 625 may becoupled via the SBC 630 to the network 610. Recipient device 645,similarly, may be coupled to the network 610 via a respective SBC and/ormedia gateway. The webservice/SIP stack 635 may similarly couple the AIvirtual assistant service 640 to the network 610.

As previously described, the end-user device 625 and/or the SBC 630 maybe configured to generate a call invite to an AI virtual assistantinstance 640 in response to a determination that the AI virtualassistant has been invoked during a call between the end-user device 625and recipient device 645. The SBC 630 may then transmit the INVITErequest to the webservice/SIP stack 635 for processing. For example, insome embodiments, the webservice/SIP stack 635 may be configured todetermine whether participants on the call (e.g., the end-user device625 and/or recipient device 645) is authorized to invoke the AI virtualassistant. The webservice/SIP stack 635 may then provision send arequest to the AI virtual assistant service 640 to provision an AIvirtual assistant instance to be connected to the call between theend-user device 625 and recipient device 645. Once provisioned, thewebservice/SIP stack 635 may then connect the AI virtual assistantinstance to the ongoing call, and an RTP conference connection may beestablished between the end-user device 625, recipient device 645, andthe AI virtual assistant service 640 (e.g., an AI virtual assistantinstance). As previously described, each AI virtual assistant instancemay be assigned a respective URI to which a connection may beestablished. In further embodiments, the AI virtual assistant instancemay be configured to receive queries and/or commands (e.g., a userinput) based on RTP media data from the call, including, withoutlimitation, voice/audio data, video data, and/or text data.

While certain features and aspects have been described with respect toexemplary embodiments, one skilled in the art will recognize thatnumerous modifications are possible. For example, the methods andprocesses described herein may be implemented using hardware components,software components, and/or any combination thereof. Further, whilevarious methods and processes described herein may be described withrespect to certain structural and/or functional components for ease ofdescription, methods provided by various embodiments are not limited toany single structural and/or functional architecture but instead can beimplemented on any suitable hardware, firmware and/or softwareconfiguration. Similarly, while certain functionality is ascribed tocertain system components, unless the context dictates otherwise, thisfunctionality can be distributed among various other system componentsin accordance with the several embodiments.

Moreover, while the procedures of the methods and processes describedherein are described in sequentially for ease of description, unless thecontext dictates otherwise, various procedures may be reordered, added,and/or omitted in accordance with various embodiments. Moreover, theprocedures described with respect to one method or process may beincorporated within other described methods or processes; likewise,system components described according to a specific structuralarchitecture and/or with respect to one system may be organized inalternative structural architectures and/or incorporated within otherdescribed systems. Hence, while various embodiments are describedwith—or without—certain features for ease of description and toillustrate exemplary aspects of those embodiments, the variouscomponents and/or features described herein with respect to oneembodiment can be substituted, added and/or subtracted from among otherdescribed embodiments, unless the context dictates otherwise.Consequently, although several exemplary embodiments are describedabove, it will be appreciated that the invention is intended to coverall modifications and equivalents within the scope of the followingclaims.

What is claimed is:
 1. A system comprising: a controller coupled to anend-user device, wherein the end-user device is configured to place awebservice call to a recipient device; a webservice stack incommunication with an in-line artificial intelligence (AI) virtualassistant service, the webservice stack comprising: a processor; andnon-transitory computer readable media comprising instructionsexecutable by the processor to: receive, from the controller, a callinvite request; provision, via the AI virtual assistant service, an AIvirtual assistant instance in response to the call invite request; andjoin the AI virtual assistant instance to the webservice call with theend-user device, wherein the AI virtual assistant instance isprovisioned to have a respective uniform resource identifier, andwherein the webservice stack is configured to connect the webservicecall to the respective uniform resource identifier associated with theAI virtual assistant instance.
 2. The system of claim 1, wherein thecontroller is configured to determine whether a user associated with theend-user device is authorized to access the AI virtual assistantservice.
 3. The system of claim 2, wherein, in response to determiningthat the user is authorized to access the AI virtual assistant service,one of the end-user device or the controller is configured toautomatically generate and transmit the call invite request to thewebservice stack.
 4. The system of claim 1, wherein the instructions toprovision the AI virtual assistant instance comprises instructionsfurther executable by the processor to: generate, in response to thecall invite request, an invoke service request to the AI virtualassistant service; transmit the invoke service request to the AI virtualassistant service, wherein the AI virtual assistant service isconfigured to provision the AI virtual assistant instance in response tothe invoke service request.
 5. The system of claim 1, wherein theinstructions to join the AI virtual assistant instance to an ongoingcall comprises instructions further executable by the processor to:establish a real-time transport protocol 2-way connection between theend-user device and the AI virtual assistant instance; and establish areal-time transport protocol conference connection between each of theend-user device, the recipient device, and the AI virtual assistantinstance.
 6. The system of claim 1 further comprising a monitoringdevice coupled to the controller, wherein the monitoring device isconfigured to determine, based on call data from the webservice call,whether a participant on the webservice call has invoked the AI virtualassistant service, wherein the monitoring device is further configuredto generate the call invite request; and wherein the controller isconfigured to join the monitoring device to the webservice call when thewebservice call is initiated by the end-user device.
 7. The system ofclaim 6, wherein determining whether the participant on the webservicecall has invoked the AI virtual assistant service includes determiningwhether the participant has performed at least one of speaking a wakeword or entering a touch tone code.
 8. The system of claim 1 wherein theAI virtual assistant instance is configured to determine whether aparticipant on the webservice call has invoked the AI virtual assistantinstance, wherein determining whether the participant has invoked the AIvirtual assistant instance includes determining whether the participantperformed at least one of speaking a wake word or entering a touch tonecode.
 9. The system of claim 1, wherein the AI virtual assistantinstance is configured to receive user input from media data of thewebservice call received over a real-time transport protocol connection,wherein media data includes at least one of audio data, text data, orvideo data.
 10. An apparatus comprising: a processor; and non-transitorycomputer readable media comprising instructions executable by theprocessor to: receive, from a controller, a webservice call inviterequest; provision, via an artificial intelligence (AI) virtualassistant service, an AI virtual assistant instance in response to thewebservice call invite request, wherein the AI virtual assistant isprovisioned with a respective uniform resource identifier; join the AIvirtual assistant instance to a webservice call with an end-user device;register the uniform resource identifier associated with the AI virtualassistant instance; and connect the uniform resource identifierassociated with the AI virtual assistant to the webservice call.
 11. Theapparatus of claim 10, wherein the instructions to provision the AIvirtual assistant instance further comprises instructions executable bythe processor to: generate, in response to the call invite request, aninvoke service request to the AI virtual assistant service; transmit theinvoke service request to the AI virtual assistant service, wherein theAI virtual assistant service is configured to provision the AI virtualassistant instance in response to the invoke service request.
 12. Theapparatus of claim 10, wherein the instructions to join the AI virtualassistant instance to an ongoing call comprises instructions furtherexecutable by the processor to: establish a real-time transport protocol2-way connection between the end-user device and the AI virtualassistant instance.
 13. The apparatus of claim 10, wherein theinstructions to join the AI virtual assistant instance to an ongoingcall comprises instructions further executable by the processor to:establish a real-time transport protocol conference connection betweeneach of the end-user device, a recipient device, and the AI virtualassistant instance.
 14. The apparatus of claim 10, wherein theinstructions are further executable by the processor to: determinewhether a user associated with the end-user device is authorized toaccess the AI virtual assistant service.
 15. A method comprising:receiving, from a controller, a call invite request; provisioning, viaan AI virtual assistant service, an artificial intelligence (AI) virtualassistant instance in response to the call invite request, wherein theAI virtual assistant is provisioned with a respective uniform resourceidentifier; joining, via a webservice stack, the AI virtual assistantinstance to a webservice call with an end-user device; registering, viathe webservice stack, the uniform resource identifier associated withthe AI virtual assistant instance; and connecting, via the webservicestack, the uniform resource identifier associated with the AI virtualassistant to the webservice call.
 16. The method of claim 15, furthercomprising: generating, via the webservice stack and in response to thecall invite request, an invoke service request; and transmitting, viathe webservice stack, the invoke service request to the AI virtualassistant service, wherein the AI virtual assistant service isconfigured to provision the AI virtual assistant instance in response tothe invoke service request.
 17. The method of claim 15, furthercomprising: establishing, via the webservice stack, a real-timetransport protocol 2-way connection between the end-user device and theAI virtual assistant instance; and establishing, via the webservicestack, al real-time transport protocol conference connection betweeneach of the end-user device, a recipient device, and the AI virtualassistant instance.